It is great we are finally getting a config for [language-server.vscode-eslint-language-server]! I have not used eslint for ages, but I am interested in making sure Helix support is as generic and unopinionated as possible. I created a discussion about it: #8452

You config seems cool, my only question is should we use experimental = { useFlatConfig = false }?

https://eslint.org/blog/2022/08/new-config-system-part-2/
https://stackoverflow.com/questions/78330131/how-do-i-configure-eslint-flat-config-with-typescript-in-vscode-without-flatco

Is FlatConfig not the current standard? Typescript ESlint seems to use it and describes the old one as legacy: https://typescript-eslint.io/getting-started/

Forgive my ignorance on this topic, I thought I would bring it up but don't really have any answers, only questions. Perhaps @Philipp-M could comment?

AFAIK eslint is almost always used within ember.js apps/addons

Ember ships with eslint per default: app blueprint

Using eslint-plugin-ember is the only way i found to get useful diagnostics

For reference, using typescript-language-server looks like this:

eslint-language-server itself isn't really that useful for things other than diagnostics and formatting so i still included typescript-language-server for that and omitted the diagnostics. This definitely isn't ideal but the best solution I found.

I just contributed my local config upstream, therefore theres things such as

[language-server.eslint.config]
experimental = { useFlatConfig = false }

If there is something like "per language" LSP configurations it would probably make sense to not configure this for other languages.

If there is something like "per language" LSP configurations it would probably make sense to not configure this for other languages.

I think each LSP config is universal in Helix.

We should probably use the equivalent of the Neovim config for eslint: https://github.com/neovim/nvim-lspconfig/blob/master/doc/server_configurations.md#eslint . It looks almost the same as the one in this PR, they also have experimental = { useFlatConfig = false }. Regarding the following from Neovim:

{
  codeActionOnSave = {
    enable = false,
    mode = "all"
}, 

My understanding is that codeActionOnSave does not work in Helix at this point, but do we want to explicitly turn it off like Neovim?